Skip to content

Conversation

@mfkl
Copy link
Member

@mfkl mfkl commented Jul 30, 2020

just checking the build

@mfkl
Copy link
Member Author

mfkl commented Aug 3, 2020

some of the failing tests are libvlc 4 regressions. Ideally, we'd need a test for each libvlc callback.

@mfkl
Copy link
Member Author

mfkl commented Aug 30, 2022

Need to have another look, this would be useful about now..

@koushikcs562
Copy link

’m interested in improving the libvlcsharp CI and test reliability. My approach would be to ensure that all tests run consistently in CI, handling regressions in libvlc 4 and disabling or adapting tests that fail due to environment-specific issues. This would involve adding targeted test tasks, fixing dead URLs, and making the CI run resilient while maintaining coverage for critical callbacks. This ensures that future contributions can be tested automatically and reliably.

@mfkl
Copy link
Member Author

mfkl commented Nov 18, 2025

feel free to open a PR, but if you're looking for an easy first issue, this isn't it

@koushikcs562
Copy link

thanks for the guidance! I’ll come up with a PR shortly. I understand it might be a bit challenging, but I see this as a great learning opportunity to improve the libvlcsharp CI and test reliability. Looking forward to contributing and getting feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants